Method and apparatus for coreset configuration of unlicensed bands

ABSTRACT

A method and apparatus in a wireless communication system is provided. The method and apparatus comprise: receiving an SS/PBCH block; determining a subcarrier spacing of the SS/PBCH block from a set of subcarrier spacings {SCS1, SCS2}; determining a subcarrier spacing of a Type0-PDCCH CSS set in a CORESET, the subcarrier spacing of the Type0-PDCCH CSS set is the same as the subcarrier spacing of the SS/PBCH block; determining a bandwidth and a number of symbols of the CORESET based on an MIB in the SS/PBCH block; determining a frequency offset from a set of frequency offsets {O1, O2}, the frequency offset is determined as being from a smallest RB index of the CORESET to a smallest RB index of the common RB overlapping with a first RB of the SS/PBCH block; determining a frequency location of the CORESET; and receiving a Type0-PDCCH.

CROSS-REFERENCE TO RELATED APPLICATIONS AND CLAIM OF PRIORITY

This application is a continuation of U.S. patent application Ser. No.17/075,477, filed Oct. 20, 2020, now U.S. Pat. No. 11,395,167, whichclaims priority to U.S. Provisional Patent Application No. 62/925,461,filed on Oct. 24, 2019; U.S. Provisional Patent Application No.62/926,924, filed on Oct. 28, 2019; U.S. Provisional Patent ApplicationNo. 62/937,362, filed on Nov. 19, 2019; and U.S. Provisional PatentApplication No. 62/957,603, filed on Jan. 6, 2020. The content of theabove-identified patent document is incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to wireless communicationsystems and, more specifically, the present disclosure relates tocontrol resource set (CORESET) configuration on unlicensed bands.

BACKGROUND

Wireless communication has been one of the most successful innovationsin modern history. Recently, the number of subscribers to wirelesscommunication services exceeded five billion and continues to growquickly. The demand of wireless data traffic is rapidly increasing dueto the growing popularity among consumers and businesses of smart phonesand other mobile data devices, such as tablets, “note pad” computers,net books, eBook readers, and machine type of devices. In order to meetthe high growth in mobile data traffic and support new applications anddeployments, improvements in radio interface efficiency and coverage isof paramount importance.

SUMMARY

The present disclosure relates to wireless communication systems and,more specifically, the present disclosure relates to CORESETconfiguration in unlicensed band.

In one embodiment, a user equipment (UE) in a wireless communicationsystem is provided. The UE comprises a transceiver configured to receivea synchronization signals and physical broadcast channel (SS/PBCH)block. The UE further comprises a processor operably connected to thetransceiver, the processor configured to: determine a subcarrier spacingof the SS/PBCH block from a set of subcarrier spacings {SCS₁, SCS₂},determine a subcarrier spacing of a type0 physical downlink controlchannel (Type0-PDCCH) common search space (CSS) set in a controlresource set (CORESET), wherein the subcarrier spacing of theType0-PDCCH CSS set is the same as the subcarrier spacing of the SS/PBCHblock, determine a bandwidth of the CORESET based on master informationblock (MIB) in the SS/PBCH block, determine a number of symbols of theCORESET based on the MIB, determine, based on the MIB and the subcarrierspacing of the SS/PBCH block, a frequency offset from a set of frequencyoffsets {O₁, O₂}, wherein the frequency offset is determined as beingfrom a smallest resource block (RB) index of the CORESET to a smallestRB index of the common RB overlapping with a first RB of the SS/PBCHblock, and determine a frequency location of the CORESET based on thedetermined frequency offset, wherein the transceiver is furtherconfigured to receive a Type0-PDCCH based on the determined bandwidth,the number of symbols, and the frequency location of the CORESET.

In another embodiment, a base station (BS) in a wireless communicationsystem is provided. The BS comprises a transceiver configured to:transmit a synchronization signals and physical broadcast channel(SS/PBCH) block; and transmit a type0 physical downlink control channel(Type0-PDCCH) based on a bandwidth, a number of symbols, and a frequencylocation of a control resource set (CORESET), wherein: the bandwidth ofthe CORESET is determined based on master information block (MIB) in theSS/PBCH block; the number of symbols of the CORESET is determined basedon the MIB; the frequency location of the CORESET is determined based ona frequency offset that is determined from a set of frequency offsets{O₁, O₂} based on the MIB and a subcarrier spacing of the SS/PBCH blockthat is determined from a set of subcarrier spacings {SCS₁, SCS₂}, thefrequency offset being determined as being from a smallest resourceblock (RB) index of the CORESET to a smallest RB index of the common RBoverlapping with a first RB of the SS/PBCH block; and a subcarrierspacing of the Type0-PDCCH common search space (CSS) set in the CORESETis configured as to the same as the subcarrier spacing of the SS/PBCHblock.

In yet another embodiment, a method of a user equipment (UE) in awireless communication system is provided. The method comprises:receiving a synchronization signals and physical broadcast channel(SS/PBCH) block; determining a subcarrier spacing of the SS/PBCH blockfrom a set of subcarrier spacings {SCS₁, SCS₂}; determining a subcarrierspacing of a type0 physical downlink control channel (Type0-PDCCH)common search space (CSS) set in a control resource set (CORESET),wherein the subcarrier spacing of the Type0-PDCCH CSS set is the same asthe subcarrier spacing of the SS/PBCH block; determining a bandwidth ofthe CORESET based on master information block (MIB) in the SS/PBCHblock; determining a number of symbols of the CORESET based on the MIB;determining, based on the MIB and the subcarrier spacing of the SS/PBCHblock, a frequency offset from a set of frequency offsets {O₁, O₂},wherein the frequency offset is determined as being from a smallestresource block (RB) index of the CORESET to a smallest RB index of thecommon RB overlapping with a first RB of the SS/PBCH block; determininga frequency location of the CORESET based on the determined frequencyoffset; and receiving a Type0-PDCCH based on the determined bandwidth,the number of symbols, and the frequency location of the CORESET.

Other technical features may be readily apparent to one skilled in theart from the following figures, descriptions, and claims.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document. The term “couple” and its derivativesrefer to any direct or indirect communication between two or moreelements, whether or not those elements are in physical contact with oneanother. The terms “transmit,” “receive,” and “communicate,” as well asderivatives thereof, encompass both direct and indirect communication.The terms “include” and “comprise,” as well as derivatives thereof, meaninclusion without limitation. The term “or” is inclusive, meaningand/or. The phrase “associated with,” as well as derivatives thereof,means to include, be included within, interconnect with, contain, becontained within, connect to or with, couple to or with, be communicablewith, cooperate with, interleave, juxtapose, be proximate to, be boundto or with, have, have a property of, have a relationship to or with, orthe like. The term “controller” means any device, system, or partthereof that controls at least one operation. Such a controller may beimplemented in hardware or a combination of hardware and software and/orfirmware. The functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely. Thephrase “at least one of,” when used with a list of items, means thatdifferent combinations of one or more of the listed items may be used,and only one item in the list may be needed. For example, “at least oneof: A, B, and C” includes any of the following combinations: A, B, C, Aand B, A and C, B and C, and A and B and C.

Moreover, various functions described below can be implemented orsupported by one or more computer programs, each of which is formed fromcomputer readable program code and embodied in a computer readablemedium. The terms “application” and “program” refer to one or morecomputer programs, software components, sets of instructions,procedures, functions, objects, classes, instances, related data, or aportion thereof adapted for implementation in a suitable computerreadable program code. The phrase “computer readable program code”includes any type of computer code, including source code, object code,and executable code. The phrase “computer readable medium” includes anytype of medium capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, acompact disc (CD), a digital video disc (DVD), or any other type ofmemory. A “non-transitory” computer readable medium excludes wired,wireless, optical, or other communication links that transporttransitory electrical or other signals. A non-transitory computerreadable medium includes media where data can be permanently stored andmedia where data can be stored and later overwritten, such as arewritable optical disc or an erasable memory device.

Definitions for other certain words and phrases are provided throughoutthis patent document. Those of ordinary skill in the art shouldunderstand that in many if not most instances, such definitions apply toprior as well as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts:

FIG. 1 illustrates an example wireless network according to embodimentsof the present disclosure;

FIG. 2 illustrates an example gNB according to embodiments of thepresent disclosure;

FIG. 3 illustrates an example UE according to embodiments of the presentdisclosure;

FIG. 4 illustrates an example DL slot structure according to embodimentsof the present disclosure;

FIG. 5 illustrates an example UL slot structure for PUSCH transmissionor PUCCH transmission according to embodiments of the presentdisclosure;

FIG. 6A illustrates an example floating CORESET #0 in carriers with 51RBs according to embodiments of the present disclosure;

FIG. 6B illustrates an example floating CORESET #0 in carriers with 50RBs according to embodiments of the present disclosure;

FIG. 6C illustrates another example floating CORESET #0 in carriers with50 RBs according to embodiments of the present disclosure;

FIG. 7 illustrates an example mapping relationship between SCSsaccording to embodiments of the present disclosure; and

FIG. 8 illustrates a flowchart of a method for configuring CORESETaccording to embodiments of the present disclosure.

DETAILED DESCRIPTION

FIG. 1 through FIG. 8 , discussed below, and the various embodimentsused to describe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged system or device.

The following documents are hereby incorporated by reference into thepresent disclosure as if fully set forth herein: 3GPP TS 38.211 v15.4.0,“NR; Physical channels and modulation”; 3GPP TS 38.212 v15.4.0, “NR;Multiplexing and Channel coding”; 3GPP TS 38.213 v15.4.0, “NR; PhysicalLayer Procedures for Control”; 3GPP TS 38.214 v15.4.0, “NR; PhysicalLayer Procedures for Data”; and 3GPP TS 38.331 v15.4.0, “NR; RadioResource Control (RRC) Protocol Specification.”

FIGS. 1-3 below describe various embodiments implemented in wirelesscommunications systems and with the use of orthogonal frequency divisionmultiplexing (OFDM) or orthogonal frequency division multiple access(OFDMA) communication techniques. The descriptions of FIGS. 1-3 are notmeant to imply physical or architectural limitations to the manner inwhich different embodiments may be implemented. Different embodiments ofthe present disclosure may be implemented in any suitably-arrangedcommunications system.

FIG. 1 illustrates an example wireless network according to embodimentsof the present disclosure. The embodiment of the wireless network shownin FIG. 1 is for illustration only. Other embodiments of the wirelessnetwork 100 could be used without departing from the scope of thisdisclosure.

As shown in FIG. 1 , the wireless network includes a gNB 101 (e.g., basestation, BS), a gNB 102, and a gNB 103. The gNB 101 communicates withthe gNB 102 and the gNB 103. The gNB 101 also communicates with at leastone network 130, such as the Internet, a proprietary Internet Protocol(IP) network, or other data network.

The gNB 102 provides wireless broadband access to the network 130 for afirst plurality of user equipments (UEs) within a coverage area 120 ofthe gNB 102. The first plurality of UEs includes a UE 111, which may belocated in a small business; a UE 112, which may be located in anenterprise (E); a UE 113, which may be located in a WiFi hotspot (HS); aUE 114, which may be located in a first residence (R); a UE 115, whichmay be located in a second residence (R); and a UE 116, which may be amobile device (M), such as a cell phone, a wireless laptop, a wirelessPDA, or the like. The gNB 103 provides wireless broadband access to thenetwork 130 for a second plurality of UEs within a coverage area 125 ofthe gNB 103. The second plurality of UEs includes the UE 115 and the UE116. In some embodiments, one or more of the gNBs 101-103 maycommunicate with each other and with the UEs 111-116 using 5G/NR, LTE,LTE-A, WiMAX, WiFi, or other wireless communication techniques.

Depending on the network type, the term “base station” or “BS” can referto any component (or collection of components) configured to providewireless access to a network, such as transmit point (TP),transmit-receive point (TRP), an enhanced base station (eNodeB or eNB),a 5G/NR base station (gNB), a macrocell, a femtocell, a WiFi accesspoint (AP), or other wirelessly enabled devices. Base stations mayprovide wireless access in accordance with one or more wirelesscommunication protocols, e.g., 5G/NR 3GPP new radio interface/access(NR), long term evolution (LTE), LTE advanced (LTE-A), high speed packetaccess (HSPA), Wi-Fi 802.11a/b/g/n/ac, etc. For the sake of convenience,the terms “BS” and “TRP” are used interchangeably in this patentdocument to refer to network infrastructure components that providewireless access to remote terminals. Also, depending on the networktype, the term “user equipment” or “UE” can refer to any component suchas “mobile station,” “subscriber station,” “remote terminal,” “wirelessterminal,” “receive point,” or “user device.” For the sake ofconvenience, the terms “user equipment” and “UE” are used in this patentdocument to refer to remote wireless equipment that wirelessly accessesa BS, whether the UE is a mobile device (such as a mobile telephone orsmartphone) or is normally considered a stationary device (such as adesktop computer or vending machine).

Dotted lines show the approximate extents of the coverage areas 120 and125, which are shown as approximately circular for the purposes ofillustration and explanation only. It should be clearly understood thatthe coverage areas associated with gNBs, such as the coverage areas 120and 125, may have other shapes, including irregular shapes, dependingupon the configuration of the gNBs and variations in the radioenvironment associated with natural and man-made obstructions.

As described in more detail below, one or more of the UEs 111-116include circuitry, programing, or a combination thereof, for efficientCORESET configuration for UEs. In certain embodiments, and one or moreof the gNBs 101-103 includes circuitry, programing, or a combinationthereof, for efficient CORESET configuration for UEs.

Although FIG. 1 illustrates one example of a wireless network, variouschanges may be made to FIG. 1 . For example, the wireless network couldinclude any number of gNBs and any number of UEs in any suitablearrangement. Also, the gNB 101 could communicate directly with anynumber of UEs and provide those UEs with wireless broadband access tothe network 130. Similarly, each gNB 102-103 could communicate directlywith the network 130 and provide UEs with direct wireless broadbandaccess to the network 130. Further, the gNBs 101, 102, and/or 103 couldprovide access to other or additional external networks, such asexternal telephone networks or other types of data networks.

FIG. 2 illustrates an example gNB 102 according to embodiments of thepresent disclosure. The embodiment of the gNB 102 illustrated in FIG. 2is for illustration only, and the gNBs 101 and 103 of FIG. 1 could havethe same or similar configuration. However, gNBs come in a wide varietyof configurations, and FIG. 2 does not limit the scope of thisdisclosure to any particular implementation of a gNB.

As shown in FIG. 2 , the gNB 102 includes multiple antennas 205 a-205 n,multiple RF transceivers 210 a-210 n, transmit (TX) processing circuitry215, and receive (RX) processing circuitry 220. The gNB 102 alsoincludes a controller/processor 225, a memory 230, and a backhaul ornetwork interface 235.

The RF transceivers 210 a-210 n receive, from the antennas 205 a-205 n,incoming RF signals, such as signals transmitted by UEs in the network100. The RF transceivers 210 a-210 n down-convert the incoming RFsignals to generate IF or baseband signals. The IF or baseband signalsare sent to the RX processing circuitry 220, which generates processedbaseband signals by filtering, decoding, and/or digitizing the basebandor IF signals. The RX processing circuitry 220 transmits the processedbaseband signals to the controller/processor 225 for further processing.

The TX processing circuitry 215 receives analog or digital data (such asvoice data, web data, e-mail, or interactive video game data) from thecontroller/processor 225. The TX processing circuitry 215 encodes,multiplexes, and/or digitizes the outgoing baseband data to generateprocessed baseband or IF signals. The RF transceivers 210 a-210 nreceive the outgoing processed baseband or IF signals from the TXprocessing circuitry 215 and up-converts the baseband or IF signals toRF signals that are transmitted via the antennas 205 a-205 n.

The controller/processor 225 can include one or more processors or otherprocessing devices that control the overall operation of the gNB 102.For example, the controller/processor 225 could control the reception offorward channel signals and the transmission of reverse channel signalsby the RF transceivers 210 a-210 n, the RX processing circuitry 220, andthe TX processing circuitry 215 in accordance with well-knownprinciples. The controller/processor 225 could support additionalfunctions as well, such as more advanced wireless communicationfunctions. For instance, the controller/processor 225 could support beamforming or directional routing operations in which outgoing/incomingsignals from/to multiple antennas 205 a-205 n are weighted differentlyto effectively steer the outgoing signals in a desired direction. Any ofa wide variety of other functions could be supported in the gNB 102 bythe controller/processor 225.

The controller/processor 225 is also capable of executing programs andother processes resident in the memory 230, such as an OS. Thecontroller/processor 225 can move data into or out of the memory 230 asrequired by an executing process.

The controller/processor 225 is also coupled to the backhaul or networkinterface 235. The backhaul or network interface 235 allows the gNB 102to communicate with other devices or systems over a backhaul connectionor over a network. The interface 235 could support communications overany suitable wired or wireless connection(s). For example, when the gNB102 is implemented as part of a cellular communication system (such asone supporting 5G/NR, LTE, or LTE-A), the interface 235 could allow thegNB 102 to communicate with other gNBs over a wired or wireless backhaulconnection. When the gNB 102 is implemented as an access point, theinterface 235 could allow the gNB 102 to communicate over a wired orwireless local area network or over a wired or wireless connection to alarger network (such as the Internet). The interface 235 includes anysuitable structure supporting communications over a wired or wirelessconnection, such as an Ethernet or RF transceiver.

The memory 230 is coupled to the controller/processor 225. Part of thememory 230 could include a RAM, and another part of the memory 230 couldinclude a Flash memory or other ROM.

Although FIG. 2 illustrates one example of gNB 102, various changes maybe made to FIG. 2 . For example, the gNB 102 could include any number ofeach component shown in FIG. 2 . As a particular example, an accesspoint could include a number of interfaces 235, and thecontroller/processor 225 could support routing functions to route databetween different network addresses. As another particular example,while shown as including a single instance of TX processing circuitry215 and a single instance of RX processing circuitry 220, the gNB 102could include multiple instances of each (such as one per RFtransceiver). Also, various components in FIG. 2 could be combined,further subdivided, or omitted and additional components could be addedaccording to particular needs.

FIG. 3 illustrates an example UE 116 according to embodiments of thepresent disclosure. The embodiment of the UE 116 illustrated in FIG. 3is for illustration only, and the UEs 111-115 of FIG. 1 could have thesame or similar configuration. However, UEs come in a wide variety ofconfigurations, and FIG. 3 does not limit the scope of this disclosureto any particular implementation of a UE.

As shown in FIG. 3 , the UE 116 includes an antenna 305, a radiofrequency (RF) transceiver 310, TX processing circuitry 315, amicrophone 320, and receive (RX) processing circuitry 325. The UE 116also includes a speaker 330, a processor 340, an input/output (I/O)interface (IF) 345, a touchscreen 350, a display 355, and a memory 360.The memory 360 includes an operating system (OS) 361 and one or moreapplications 362.

The RF transceiver 310 receives, from the antenna 305, an incoming RFsignal transmitted by a gNB of the network 100. The RF transceiver 310down-converts the incoming RF signal to generate an intermediatefrequency (IF) or baseband signal. The IF or baseband signal is sent tothe RX processing circuitry 325, which generates a processed basebandsignal by filtering, decoding, and/or digitizing the baseband or IFsignal. The RX processing circuitry 325 transmits the processed basebandsignal to the speaker 330 (such as for voice data) or to the processor340 for further processing (such as for web browsing data).

The TX processing circuitry 315 receives analog or digital voice datafrom the microphone 320 or other outgoing baseband data (such as webdata, e-mail, or interactive video game data) from the processor 340.The TX processing circuitry 315 encodes, multiplexes, and/or digitizesthe outgoing baseband data to generate a processed baseband or IFsignal. The RF transceiver 310 receives the outgoing processed basebandor IF signal from the TX processing circuitry 315 and up-converts thebaseband or IF signal to an RF signal that is transmitted via theantenna 305.

The processor 340 can include one or more processors or other processingdevices and execute the OS 361 stored in the memory 360 in order tocontrol the overall operation of the UE 116. For example, the processor340 could control the reception of forward channel signals and thetransmission of reverse channel signals by the RF transceiver 310, theRX processing circuitry 325, and the TX processing circuitry 315 inaccordance with well-known principles. In some embodiments, theprocessor 340 includes at least one microprocessor or microcontroller.

The processor 340 is also capable of executing other processes andprograms resident in the memory 360, such as processes for beammanagement. The processor 340 can move data into or out of the memory360 as required by an executing process. In some embodiments, theprocessor 340 is configured to execute the applications 362 based on theOS 361 or in response to signals received from gNBs or an operator. Theprocessor 340 is also coupled to the I/O interface 345, which providesthe UE 116 with the ability to connect to other devices, such as laptopcomputers and handheld computers. The I/O interface 345 is thecommunication path between these accessories and the processor 340.

The processor 340 is also coupled to the touchscreen 350 and the display355. The operator of the UE 116 can use the touchscreen 350 to enterdata into the UE 116. The display 355 may be a liquid crystal display,light emitting diode display, or other display capable of rendering textand/or at least limited graphics, such as from web sites.

The memory 360 is coupled to the processor 340. Part of the memory 360could include a random access memory (RAM), and another part of thememory 360 could include a Flash memory or other read-only memory (ROM).

Although FIG. 3 illustrates one example of UE 116, various changes maybe made to FIG. 3 . For example, various components in FIG. 3 could becombined, further subdivided, or omitted and additional components couldbe added according to particular needs. As a particular example, theprocessor 340 could be divided into multiple processors, such as one ormore central processing units (CPUs) and one or more graphics processingunits (GPUs). Also, while FIG. 3 illustrates the UE 116 configured as amobile telephone or smartphone, UEs could be configured to operate asother types of mobile or stationary devices.

To meet the demand for wireless data traffic having increased sincedeployment of 4G communication systems and to enable various verticalapplications, efforts have been made to develop and deploy an improved5G/NR or pre-5G/NR communication system. Therefore, the 5G/NR orpre-5G/NR communication system is also called a “beyond 4G network” or a“post LTE system.” The 5G/NR communication system is considered to beimplemented in higher frequency (mmWave) bands, e.g., 28 GHz or 60 GHzbands, so as to accomplish higher data rates or in lower frequencybands, such as 6 GHz, to enable robust coverage and mobility support.Aspects of the present disclosure may also be applied to deployment of5G communication systems, 6G or even later releases which may useterahertz (THz) bands. To decrease propagation loss of the radio wavesand increase the transmission distance, the beamforming, massivemultiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO),array antenna, an analog beam forming, large scale antenna techniquesare discussed in 5G/NR communication systems.

In addition, in 5G/NR communication systems, development for systemnetwork improvement is under way based on advanced small cells, cloudradio access networks (RANs), ultra-dense networks, device-to-device(D2D) communication, wireless backhaul, moving network, cooperativecommunication, coordinated multi-points (CoMP), reception-endinterference cancellation and the like.

A communication system includes a downlink (DL) that refers totransmissions from a base station or one or more transmission points toUEs and an uplink (UL) that refers to transmissions from UEs to a basestation or to one or more reception points.

A time unit for DL signaling or for UL signaling on a cell is referredto as a slot and can include one or more symbols. A symbol can alsoserve as an additional time unit. A frequency (or bandwidth (BW)) unitis referred to as a resource block (RB). One RB includes a number ofsub-carriers (SCs). For example, a slot can have duration of 0.5milliseconds or 1 millisecond, include 14 symbols and an RB can include12 SCs with inter-SC spacing of 15 KHz or 30 KHz, and so on.

DL signals include data signals conveying information content, controlsignals conveying DL control information (DCI), and reference signals(RS) that are also known as pilot signals. A gNB transmits datainformation or DCI through respective physical DL shared channels(PDSCHs) or physical DL control channels (PDCCHs). A PDSCH or a PDCCHcan be transmitted over a variable number of slot symbols including oneslot symbol. For brevity, a DCI format scheduling a PDSCH reception by aUE is referred to as a DL DCI format and a DCI format scheduling a PUSCHtransmission from a UE is referred to as an UL DCI format.

A gNB transmits one or more of multiple types of RS including channelstate information RS (CSI-RS) and demodulation RS (DMRS). A CSI-RS isprimarily intended for UEs to perform measurements and provide channelstate information (CSI) to a gNB. For channel measurement, non-zeropower CSI-RS (NZP CSI-RS) resources are used. For interferencemeasurement reports (IMRs), CSI interference measurement (CSI-IM)resources associated with a zero power CSI-RS (ZP CSI-RS) configurationare used. A CSI process consists of NZP CSI-RS and CSI-IM resources.

A UE can determine CSI-RS transmission parameters through DL controlsignaling or higher layer signaling, such as radio resource control(RRC) signaling, from a gNB. Transmission instances of a CSI-RS can beindicated by DL control signaling or be configured by higher layersignaling. A DMRS is transmitted only in the BW of a respective PDCCH orPDSCH and a UE can use the DMRS to demodulate data or controlinformation.

FIG. 4 and FIG. 5 illustrate example wireless transmit and receive pathsaccording to this disclosure. In the following description, a transmitpath 400 may be described as being implemented in an gNB (such as gNB102), while a receive path 500 may be described as being implemented ina UE (such as UE 116). However, it may be understood that the receivepath 500 can be implemented in an gNB and that the transmit path 400 canbe implemented in a UE. In some embodiments, the receive path 500 isconfigured to support the codebook design and structure for systemshaving 2D antenna arrays as described in embodiments of the presentdisclosure.

The transmit path 400 as illustrated in FIG. 4 includes a channel codingand modulation block 405, a serial-to-parallel (S-to-P) block 410, asize N inverse fast Fourier transform (IFFT) block 415, aparallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425,and an up-converter (UC) 430. The receive path 500 as illustrated inFIG. 5 includes a down-converter (DC) 555, a remove cyclic prefix block560, a serial-to-parallel (S-to-P) block 565, a size N fast Fouriertransform (FFT) block 570, a parallel-to-serial (P-to-S) block 575, anda channel decoding and demodulation block 580.

As illustrated in FIG. 400 , the channel coding and modulation block 405receives a set of information bits, applies coding (such as alow-density parity check (LDPC) coding), and modulates the input bits(such as with quadrature phase shift keying (QPSK) or quadratureamplitude modulation (QAM)) to generate a sequence of frequency-domainmodulation symbols.

The serial-to-parallel block 410 converts (such as de-multiplexes) theserial modulated symbols to parallel data in order to generate Nparallel symbol streams, where N is the IFFT/FFT size used in the gNB102 and the UE 116. The size N IFFT block 415 performs an IFFT operationon the N parallel symbol streams to generate time-domain output signals.The parallel-to-serial block 420 converts (such as multiplexes) theparallel time-domain output symbols from the size N IFFT block 415 inorder to generate a serial time-domain signal. The add cyclic prefixblock 425 inserts a cyclic prefix to the time-domain signal. Theup-converter 430 modulates (such as up-converts) the output of the addcyclic prefix block 425 to an RF frequency for transmission via awireless channel. The signal may also be filtered at baseband beforeconversion to the RF frequency.

A transmitted RF signal from the gNB 102 arrives at the UE 116 afterpassing through the wireless channel, and reverse operations to those atthe gNB 102 are performed at the UE 116.

As illustrated in FIG. 5 , the down-converter 555 down-converts thereceived signal to a baseband frequency, and the remove cyclic prefixblock 560 removes the cyclic prefix to generate a serial time-domainbaseband signal. The serial-to-parallel block 565 converts thetime-domain baseband signal to parallel time domain signals. The size NFFT block 570 performs an FFT algorithm to generate N parallelfrequency-domain signals. The parallel-to-serial block 575 converts theparallel frequency-domain signals to a sequence of modulated datasymbols. The channel decoding and demodulation block 580 demodulates anddecodes the modulated symbols to recover the original input data stream.

Each of the gNBs 101-103 may implement a transmit path 400 asillustrated in FIG. 4 that is analogous to transmitting in the downlinkto UEs 111-116 and may implement a receive path 500 as illustrated inFIG. 5 that is analogous to receiving in the uplink from UEs 111-116.Similarly, each of UEs 111-116 may implement the transmit path 400 fortransmitting in the uplink to gNBs 101-103 and may implement the receivepath 500 for receiving in the downlink from gNBs 101-103.

Each of the components in FIG. 4 and FIG. 5 can be implemented usingonly hardware or using a combination of hardware and software/firmware.As a particular example, at least some of the components in FIG. 4 andFIG. 5 may be implemented in software, while other components may beimplemented by configurable hardware or a mixture of software andconfigurable hardware. For instance, the FFT block 570 and the IFFTblock 515 may be implemented as configurable software algorithms, wherethe value of size N may be modified according to the implementation.

Furthermore, although described as using FFT and IFFT, this is by way ofillustration only and may not be construed to limit the scope of thisdisclosure. Other types of transforms, such as discrete Fouriertransform (DFT) and inverse discrete Fourier transform (IDFT) functions,can be used. It may be appreciated that the value of the variable N maybe any integer number (such as 1, 2, 3, 4, or the like) for DFT and IDFTfunctions, while the value of the variable N may be any integer numberthat is a power of two (such as 1, 2, 4, 8, 16, or the like) for FFT andIFFT functions.

Although FIG. 4 and FIG. 5 illustrate examples of wireless transmit andreceive paths, various changes may be made to FIG. 4 and FIG. 5 . Forexample, various components in FIG. 4 and FIG. 5 can be combined,further subdivided, or omitted and additional components can be addedaccording to particular needs. Also, FIG. 4 and FIG. 5 are meant toillustrate examples of the types of transmit and receive paths that canbe used in a wireless network. Any other suitable architectures can beused to support wireless communications in a wireless network.

The present disclosure provides the mechanism and methodology to enabledetermining the offset between SS/PBCH block (SSB) and CORESET #0 for anunlicensed band, wherein CORESET #0 is the control resource set fortype0 PDCCH. The present disclosure includes the following components:frequency domain offset for CORESET #0, sub-RB-level offset indication;and CORESET #0 configuration.

The present disclosure provides the configuration of CORESET #0(including the frequency domain offset) for unlicensed band (e.g.,operation with shared spectrum channel access), taking intoconsideration of different character of synchronization raster andchannel raster design difference between licensed band and unlicensedband, wherein the configuration of CORESET #0 can be included in the MIBof an SSB.

In one embodiment, the frequency domain offset between SS/PBCH block(e.g., SSB) and CORESET #0 is defined as the difference between thelowest RE of SS/PBCH block and the lowest RE of the associated CORESET#0, wherein the offset includes a RB-level offset (e.g., with respect tothe subcarrier spacing (SCS) of CORESET #0) and a sub-RB-level offset(e.g., with respect to the SCS of 15 kHz for FR1). In one example, thesub-RB-level offset also defines the offset between lowest RE of SSB andthe common resource grid.

In one example, the channel raster for a given carrier bandwidth isfixed, in unlicensed band. In another example, the synchronizationraster within a nominal carrier bandwidth (e.g., 20 MHz) is fixed.

In one example, the frequency offset between the SSB and CORESET #0,when the CORESET #0 is located at the lowest edge of the channel, can becalculated based on the fixed synchronization raster and fixed channelraster, for a given carrier bandwidth and a given combination of SCS ofSSB and CORESET #0.

In one example, RB-level offset can be given byΔF_RB=floor(ΔF/(SCS_CORESET*N_SC)); and sub-RB-level offset can be givenby ΔF_subRB=(ΔF−(SCS_CORESET*N_SC)*ΔF_RB)/SCS_ref; whereinΔF=(F_sync−N_SSB/2*SCS_SSB*N_SC)−(F_channel−N_carrier/2*SCS_CORESET*N_SC),and F_sync is the frequency of synchronization raster entry, F_channelis the frequency of channel raster entry, N_SSB is the number of RBs forSSB bandwidth (e.g., 20 RB), N_carrier is the number of RBs for carrierbandwidth, SCS_SSB is the subcarrier spacing of SSB, SCS_CORESET is thesubcarrier spacing of CORESET #0, N_SC is the number of subcarriers in aRB (e.g., 12), SCC_ref is the reference subcarrier spacing for definingthe common resource grid (e.g., 15 kHz for FR1).

Example offsets are given by TABLE 1-1, for 20 MHz channel and {SCS_SSB,SCS_CORESET} {30 kHz, 30 kHz}.

TABLE 1-1 Example offsets for 20 MHz channel and {SCS_SSB, SCS_CORESET}= {30 kHz, 30 kHz} lowest Nominal lowest synchronization RE of channelRE of Sub-RB- raster F_sync SSB center F_channel channel RB-level levelindex (GSCN) (MHz) (MHz) (MHz) (MHz) (MHz) offset offset 1 8996 5155.685152.08 5160 5160 5150.82 3 12 2 9010 5175.84 5172.24 5180 5179.985170.8 4 0 3 9024 5196 5192.4 5200 5200.02 5190.84 4 8 4 9037 5214.725211.12 5220 5220 5210.82 0 20 or or or or or 9038 5216.16 5212.56 4 205 9051 5234.88 5231.28 5240 5239.98 5230.8 1 8 6 9065 5255.04 5251.445260 5260.02 5250.84 1 16 7 9079 5275.2 5271.6 5280 5280 5270.82 2 4 89093 5295.36 5291.76 5300 5299.98 5290.8 2 16 9 9107 5315.52 5311.925320 5320.02 5310.84 3 0 10 9121 5335.68 5332.08 5340 5340 5330.82 3 1211 9218 5475.36 5471.76 5480 5479.98 5470.8 2 16 12 9232 5495.52 5491.925500 5500.02 5490.84 3 0 13 9246 5515.68 5512.08 5520 5520 5510.82 3 1214 9260 5535.84 5532.24 5540 5539.98 5530.8 4 0 15 9274 5556 5552.4 55605560.02 5550.84 4 8 16 9287 5574.72 5571.12 5580 5580 5570.82 0 20 179301 5594.88 5591.28 5600 5599.98 5590.8 1 8 18 9315 5615.04 5611.445620 5620.02 5610.84 1 16 19 9329 5635.2 5631.6 5640 5640 5630.82 2 4 209343 5655.36 5651.76 5660 5659.98 5650.8 2 16 21 9357 5675.52 5671.925680 5680.02 5670.84 3 0 22 9371 5695.68 5692.08 5700 5700 5690.82 3 1223 9385 5715.84 5712.24 5720 5719.98 5710.8 4 0 24 9402 5740.32 5736.725745 5745 5735.82 2 12 25 9416 5760.48 5756.88 5765 5764.98 5755.8 3 026 9430 5780.64 5777.04 5785 5785.02 5775.84 3 8 27 9444 5800.8 5797.25805 5805 5795.82 3 20 28 9458 5820.96 5817.36 5825 5824.98 5815.8 4 829 9471 5839.68 5836.08 5845 5845.02 5835.84 0 16 30 9485 5859.845856.24 5865 5865 5855.82 1 4 31 9499 5880 5876.4 5885 5884.98 5875.8 116 32 9513 5900.16 5896.56 5905 5905.02 5895.84 2 0

Example offsets are given by TABLE 1-2, for 40 MHz channel and {SCS_SSB,SCS_CORESET}={30 kHz, 30 kHz}.

TABLE 1-2 Example offsets for 40 MHz channel and {SCS_SSB, SCS_CORESET}= {30 kHz, 30 kHz} lowest Nominal lowest synchronization RE of channelRE of Sub-RB- raster F_sync SSB center F_channel channel RB-level levelindex (GSCN) (MHz) (MHz) (MHz) (MHz) (MHz) offset offset 1 8996 5155.685152.08 5170 5170.02 5150.94 3 4 2 9010 5175.84 5172.24 5190 51905170.92 3 16 3 9024 5196 5192.4 4 9037 5214.72 5211.12 5230 5230.025210.94 0 12 or or or or or 9038 5216.16 5212.56 4 12 5 9051 5234.885231.28 6 9065 5255.04 5251.44 5270 5269.98 5250.9 1 12 7 9079 5275.25271.6 8 9093 5295.36 5291.76 5310 5310 5290.92 2 8 9 9107 5315.525311.92 5330 5329.98 5310.9 2 20 10 9121 5335.68 5332.08 11 9218 5475.365471.76 5490 5490 5470.92 2 8 12 9232 5495.52 5491.92 5510 5509.985490.9 2 20 13 9246 5515.68 5512.08 14 9260 5535.84 5532.24 5550 55505530.92 3 16 15 9274 5556 5552.4 16 9287 5574.72 5571.12 5590 5590.025570.94 0 12 17 9301 5594.88 5591.28 18 9315 5615.04 5611.44 56305629.98 5610.9 1 12 19 9329 5635.2 5631.6 20 9343 5655.36 5651.76 56705670 5650.92 2 8 21 9357 5675.52 5671.92 22 9371 5695.68 5692.08 57105710.02 5690.94 3 4 23 9385 5715.84 5712.24 24 9402 5740.32 5736.72 57555755.02 5735.94 2 4 25 9416 5760.48 5756.88 26 9430 5780.64 5777.04 57955794.98 5775.9 3 4 27 9444 5800.8 5797.2 5815 5815.02 5795.94 3 12 289458 5820.96 5817.36 5835 5835 5815.92 4 0 29 9471 5839.68 5836.08 309485 5859.84 5856.24 5875 5875.02 5855.94 0 20 31 9499 5880 5876.4 329513 5900.16 5896.56

Example offsets are given by TABLE 1-3, for 60 MHz channel and {SCS_SSB,SCS_CORESET}={30 kHz, 30 kHz}.

TABLE 1-3 Example offsets for 60 MHz channel and {SCS_SSB, SCS_CORESET}= {30 kHz, 30 kHz} lowest Nominal lowest synchronization RE of channelRE of Sub-RB- raster F_sync SSB center F_channel channel RB-level levelindex (GSCN) (MHz) (MHz) (MHz) (MHz) (MHz) offset offset 1 8996 5155.685152.08 5180 5179.98 5150.82 3 12 2 9010 5175.84 5172.24 5200 5200.025170.86 3 20 3 9024 5196 5192.4 5220 5220 5190.84 4 8 4 9037 5214.725211.12 or or or 9038 5216.16 5212.56 5 9051 5234.88 5231.28 6 90655255.04 5251.44 5280 5280 5250.84 1 16 7 9079 5275.2 5271.6 5300 5299.985270.82 2 4 8 9093 5295.36 5291.76 5320 5320.02 5290.86 2 12 9 91075315.52 5311.92 10 9121 5335.68 5332.08 11 9218 5475.36 5471.76 55005500.02 5470.86 2 12 12 9232 5495.52 5491.92 5520 5520 5490.84 3 0 139246 5515.68 5512.08 5540 5539.98 5510.82 3 12 14 9260 5535.84 5532.2415 9274 5556 5552.4 5580 5580 5550.84 4 8 16 9287 5574.72 5571.12 56005599.98 5570.82 0 20 17 9301 5594.88 5591.28 5620 5620.02 5590.86 1 4 189315 5615.04 5611.44 19 9329 5635.2 5631.6 20 9343 5655.36 5651.76 56805680.02 5650.86 2 12 21 9357 5675.52 5671.92 5700 5700 5670.84 3 0 229371 5695.68 5692.08 23 9385 5715.84 5712.24 24 9402 5740.32 5736.725765 5764.98 5735.82 2 12 25 9416 5760.48 5756.88 5785 5785.02 5755.86 220 26 9430 5780.64 5777.04 5805 5805 5775.84 3 8 27 9444 5800.8 5797.228 9458 5820.96 5817.36 29 9471 5839.68 5836.08 30 9485 5859.84 5856.2431 9499 5880 5876.4 32 9513 5900.16 5896.56

Example offsets are given by TABLE 1-4, for 80 MHz channel and {SCS_SSB,SCS_CORESET}={30 kHz, 30 kHz}.

TABLE 1-4 Example offsets for 80 MHz channel and {SCS_SSB, SCS_CORESET}= {30 kHz, 30 kHz} lowest Nominal lowest synchronization RE of channelRE of Sub-RB- raster F_sync SSB center F_channel channel RB-level levelindex (GSCN) (MHz) (MHz) (MHz) (MHz) (MHz) offset offset 1 8996 5155.685152.08 5190 5190 5150.94 3 4 2 9010 5175.84 5172.24 5210 5209.985170.92 3 16 3 9024 5196 5192.4 4 9037 5214.72 5211.12 or or or 90385216.16 5212.56 5 9051 5234.88 5231.28 6 9065 5255.04 5251.44 52905290.02 5250.96 1 8 7 9079 5275.2 5271.6 8 9093 5295.36 5291.76 9 91075315.52 5311.92 10 9121 5335.68 5332.08 11 9218 5475.36 5471.76 12 92325495.52 5491.92 5530 5530.02 5490.96 2 16 13 9246 5515.68 5512.08 149260 5535.84 5532.24 15 9274 5556 5552.4 16 9287 5574.72 5571.12 56105610 5570.94 0 12 17 9301 5594.88 5591.28 18 9315 5615.04 5611.44 199329 5635.2 5631.6 20 9343 5655.36 5651.76 5690 5689.98 5650.92 2 8 219357 5675.52 5671.92 22 9371 5695.68 5692.08 23 9385 5715.84 5712.24 249402 5740.32 5736.72 5775 5775 5735.94 2 4 25 9416 5760.48 5756.88 57955794.98 5755.92 2 16 26 9430 5780.64 5777.04 27 9444 5800.8 5797.2 289458 5820.96 5817.36 5855 5854.98 5815.92 4 0 29 9471 5839.68 5836.08 309485 5859.84 5856.24 31 9499 5880 5876.4 32 9513 5900.16 5896.56

Example offsets are given by TABLE 1-5, for 20 MHz channel and {SCS_SSB,SCS_CORESET} {15 kHz, 15 kHz}.

TABLE 1-5 Example offsets for 20 MHz channel and {SCS_SSB, SCS_CORESET}= {15 kHz, 15 kHz} lowest Nominal lowest synchronization RE of channelRE of Sub-RB- raster F_sync SSB center F_channel channel RB-level levelindex (GSCN) (MHz) (MHz) (MHz) (MHz) (MHz) offset offset 1 8996 5155.685153.88 5160 5160 5150.46 19 0 2 9010 5175.84 5174.04 5180 5179.985170.44 20 0 3 9024 5196 5194.2 5200 5200.02 5190.48 20 8 4 9037 5214.725211.12 5220 5220 5210.46 13 8 or or or or or 9038 5216.16 5214.36 21 85 9051 5234.88 5233.08 5240 5239.98 5230.44 14 8 6 9065 5255.04 5253.245260 5260.02 5250.48 15 4 7 9079 5275.2 5273.4 5280 5280 5270.46 16 4 89093 5295.36 5293.56 5300 5299.98 5290.44 17 4 9 9107 5315.52 5313.725320 5320.02 5310.48 18 0 10 9121 5335.68 5333.88 5340 5340 5330.46 19 011 9218 5475.36 5473.56 5480 5479.98 5470.44 17 4 12 9232 5495.525493.72 5500 5500.02 5490.48 18 0 13 9246 5515.68 5513.88 5520 55205510.46 19 0 14 9260 5535.84 5534.04 5540 5539.98 5530.44 20 0 15 92745556 5554.2 5560 5560.02 5550.48 20 8 16 9287 5574.72 5572.92 5580 55805570.46 13 8 17 9301 5594.88 5593.08 5600 5599.98 5590.44 14 8 18 93155615.04 5613.24 5620 5620.02 5610.48 15 4 19 9329 5635.2 5633.4 56405640 5630.46 16 4 20 9343 5655.36 5653.56 5660 5659.98 5650.44 17 4 219357 5675.52 5673.72 5680 5680.02 5670.48 18 0 22 9371 5695.68 5693.885700 5700 5690.46 19 0 23 9385 5715.84 5714.04 5720 5719.98 5710.44 20 024 9402 5740.32 5738.52 5745 5745 5735.46 17 0 25 9416 5760.48 5758.685765 5764.98 5755.44 18 0 26 9430 5780.64 5778.84 5785 5785.02 5775.4818 8 27 9444 5800.8 5799 5805 5805 5795.46 19 8 28 9458 5820.96 5819.165825 5824.98 5815.44 20 8 29 9471 5839.68 5837.88 5845 5845.02 5835.4813 4 30 9485 5859.84 5858.04 5865 5865 5855.46 14 4 31 9499 5880 5878.25885 5884.98 5875.44 15 4 32 9513 5900.16 5898.36 5905 5905.02 5895.4816 0

Example offsets are given by TABLE 1-6, for 40 MHz channel and {SCS_SSB,SCS_CORESET}={15 kHz, 15 kHz}.

TABLE 1-6 Example offsets for 40 MHz channel and {SCS_SSB, SCS_CORESET}= {15 kHz, 15 kHz} lowest Nominal lowest synchronization RE of channelRE of Sub-RB- raster F_sync SSB center F_channel channel RB-level levelindex (GSCN) (MHz) (MHz) (MHz) (MHz) (MHz) offset offset 1 8996 5155.685153.88 5170 5170.02 5150.58 18 4 2 9010 5175.84 5174.04 5190 51905170.56 19 4 3 9024 5196 5194.2 4 9037 5214.72 5211.12 5230 5230.025210.58 13 0 or or or or or 9038 5216.16 5214.36 21 0 5 9051 5234.885233.08 6 9065 5255.04 5253.24 5270 5269.98 5250.54 15 0 7 9079 5275.25273.4 8 9093 5295.36 5293.56 5310 5310 5290.56 16 8 9 9107 5315.525313.72 5330 5329.98 5310.54 17 8 10 9121 5335.68 5333.88 11 92185475.36 5473.56 5490 5490 5470.56 16 8 12 9232 5495.52 5493.72 55105509.98 5490.54 17 8 13 9246 5515.68 5513.88 14 9260 5535.84 5534.045550 5550 5530.56 19 4 15 9274 5556 5554.2 16 9287 5574.72 5572.92 55905590.02 5570.58 13 0 17 9301 5594.88 5593.08 18 9315 5615.04 5613.245630 5629.98 5610.54 15 0 19 9329 5635.2 5633.4 20 9343 5655.36 5653.565670 5670 5650.56 16 8 21 9357 5675.52 5673.72 22 9371 5695.68 5693.885710 5710.02 5690.58 18 4 23 9385 5715.84 5714.04 24 9402 5740.325738.52 5755 5755.02 5735.58 16 4 25 9416 5760.48 5758.68 26 94305780.64 5778.84 5795 5794.98 5775.54 18 4 27 9444 5800.8 5799 58155815.02 5795.58 19 0 28 9458 5820.96 5819.16 5835 5835 5815.56 20 0 299471 5839.68 5837.88 30 9485 5859.84 5858.04 5875 5875.02 5855.58 13 831 9499 5880 5878.2 32 9513 5900.16 5898.36

In another example, the frequency offset between the SSB and CORESET #0,when the CORESET #0 is located at the highest edge of the channel, canbe calculated based on the fixed synchronization raster and fixedchannel raster, for a given carrier bandwidth and a given combination ofSCS of SSB and CORESET #0.

In one example, RB-level offset can be given byΔF_RB=N_CORESET−ceiling(ΔF/(SCS_CORESET*N_SC))−N_SSB; and sub-RB-leveloffset can be given byΔF_subRB=(N_CORESET+(SCS_CORESET*N_SC)*ΔF_RB+N_SSB−ΔF)/SCS_ref; whereinΔF=(F_channel+N_carrier/2*SCS_CORESET*N_SC)−(F_sync+N_SSB/2*SCS_SSB*N_SC),and F_sync is the frequency of synchronization raster entry, F_channelis the frequency of channel raster entry, N_SSB is the number of RBs forSSB bandwidth (e.g., 20 RB), N_carrier is the number of RBs for carrierbandwidth, N_CORESET is the number of RBs for CORESET #0, SCS_SSB is thesubcarrier spacing of SSB, SCS_CORESET is the subcarrier spacing ofCORESET #0, N_SC is the number of subcarriers in a RB (e.g., 12),SCC_ref is the reference subcarrier spacing for defining the commonresource grid (e.g., 15 kHz for FR1).

A summary of the RB-level offset and RE-level offset for channels withall supported bandwidth is shown in TABLE 2-1 to TABLE 2-4.

TABLE 2-1 Example offsets for 20 MHz channel. RB-level Sub-RB- RB-levelSub-RB- Nominal Channel offset for level offset offset for level offsetChannel channel center raster Sync raster 30 kHz for 30 kHz 15 kHz for15 kHz index (MHz) (MHz) (GSCN) SCS SCS SCS SCS 1 5160 5160.00 8996 3 1219 0 2 5180 5179.98 9010 4 0 20 0 3 5200 5200.02 9024 4 8 20 8 4 52205220.00 9037 0 20 13 8 or 9038 or 4 or 20 or 21 or 8 5 5240 5239.98 90511 8 14 8 6 5260 5260.02 9065 1 16 15 4 7 5280 5280.00 9079 2 4 16 4 85300 5299.98 9093 2 16 17 4 9 5320 5320.02 9107 3 0 18 0 10 5340 5340.009121 3 12 19 0 11 5480 5479.98 9218 2 16 17 4 12 5500 5500.02 9232 3 018 0 13 5520 5520.00 9246 3 12 19 0 14 5540 5539.98 9260 4 0 20 0 155560 5560.02 9274 4 8 20 8 16 5580 5580.00 9287 0 20 13 8 17 56005599.98 9301 1 8 14 8 18 5620 5620.02 9315 1 16 15 4 19 5640 5640.009329 2 4 16 4 20 5660 5659.98 9343 2 16 17 4 21 5680 5680.02 9357 3 0 180 22 5700 5700.00 9371 3 12 19 0 23 5720 5719.98 9385 4 0 20 0 24 57455745.00 9402 2 12 17 0 25 5765 5764.98 9416 3 0 18 0 26 5785 5785.029430 3 8 18 8 27 5805 5805.00 9444 3 20 19 8 28 5825 5824.98 9458 4 8 208 29 5845 5845.02 9471 0 16 13 4 30 5865 5865.00 9485 1 4 14 4 31 58855884.98 9499 1 16 15 4 32 5905 5905.02 9513 2 0 16 0

TABLE 2-2 Example offsets for 40 MHz channel. Channel RB-level Sub-RB-RB-level Sub-RB- Nominal raster offset for level offset offset for leveloffset Channel channel center F_channel Sync raster 30 kHz for 30 kHz 15kHz for 15 kHz index (MHz) (MHz) (GSCN) SCS SCS SCS SCS 1 5170 5170.028996 3 4 18 4 9010 4 20 2 5190 5190.00 9010 3 16 19 4 9024 4 21 3 52305230.02 9037 0 12 13 0 or 9038 or 4 9051 1 15 4 5270 5269.98 9065 1 1215 0 9079 2 17 5 5310 5310.00 9093 2 8 16 8 9107 3 18 6 5330 5329.989107 2 20 17 8 9121 3 19 7 5490 5490.00 9218 2 8 16 8 9232 3 18 8 55105509.98 9232 2 20 17 8 9246 3 19 9 5550 5550.00 9260 3 16 19 4 9274 4 2110 5590 5590.02 9287 0 12 13 0 9301 1 15 11 5630 5629.98 9315 1 12 15 09329 2 17 12 5670 5670.00 9343 2 8 16 8 9357 3 18 13 5710 5710.02 9371 34 18 4 9385 4 20 14 5755 5755.02 9402 2 4 16 4 9416 3 18 15 5795 5794.989430 3 4 18 4 9444 4 20 16 5815 5815.02 9444 3 12 19 0 9458 4 21 17 58355835.00 9458 4 0 20 0 9471 1 14 18 5875 5875.02 9485 0 20 13 8 9499 1 15

TABLE 2-3 Example offsets for 60 MHz channel. Channel RB-level Sub-RB-RB-level Sub-RB- Nominal raster offset for level offset offset for leveloffset Channel channel center F_channel Sync raster 30 kHz for 30 kHz 15kHz for 15 kHz index (MHz) (MHz) (GSCN) SCS SCS SCS SCS 1 5180 5155.688996 3 12 — — 9024 4 — 2 5200 5175.84 9010 3 — 9037 0 20 — — or 9038 or4 3 5220 5196.00 9024 4 8 — — 9051 1 — 4 5280 5255.04 9065 1 16 — — 90932 — 5 5300 5275.20 9079 2 4 — — 9107 3 — 6 5320 5295.36 9093 2 12 — —9121 3 — 7 5500 5475.36 9218 2 12 — — 9246 3 — 8 5520 5495.52 9232 3 0 —— 9260 4 — 9 5540 5515.68 9246 3 12 — — 9274 4 — 10 5580 5556.00 9274 48 — — 9301 1 — 11 5600 5574.72 9287 0 20 — — 9315 1 — 12 5620 5594.889301 1 4 — — 9329 2 — 13 5680 5655.36 9343 2 12 — — 9371 3 — 14 57005675.52 9357 3 0 — — 9385 4 — 15 5765 5740.32 9402 2 12 — — 9430 3 — 165785 5760.48 9416 2 20 — — 9444 3 — 17 5805 5780.64 9430 3 8 — — 9458 4—

TABLE 2-4 Example offsets for 80 MHz channel. Channel RB-level Sub-RB-RB-level Sub-RB- Nominal raster offset for level offset offset for leveloffset Channel channel center F_channel Sync raster 30 kHz for 30 kHz 15kHz for 15 kHz index (MHz) (MHz) (GSCN) SCS SCS SCS SCS 1 5190 5190.008996 3 4 — — 9037 1 — or 9038 or 5 2 5210 5209.98 9010 3 16 — — 9051 1 —3 5290 5290.02 9065 1 8 — — 9107 3 — 4 5530 5530.02 9232 2 16 — — 9274 4— 5 5610 5610.00 9287 0 12 — — 9329 2 — 6 5690 5689.98 9343 2 8 — — 93854 — 7 5775 5775.00 9402 2 4 — — 9444 4 — 8 5795 5794.98 9416 2 16 — —9458 4 — 9 5855 5854.98 9458 4 0 — — 9499 2 —

FIG. 6A illustrates an example floating CORESET #0 in carriers with 51RBs 600 according to embodiments of the present disclosure. Anembodiment of the floating CORESET #0 in carriers with 51 RBs 600 shownin FIG. 6A is for illustration only. One or more of the componentsillustrated in FIG. 6A can be implemented in specialized circuitryconfigured to perform the noted functions or one or more of thecomponents can be implemented by one or more processors executinginstructions to perform the noted functions.

In one example, for the channelization of 20 MHz LBT bandwidth as 51 RBswith respect to 30 kHz, for each given channel supported in NR-U, thepossible offsets are illustrated in FIG. 6A, and the corresponding tableis given in TABLE 3-1. Then, two CORESET #0 offsets selected as (0, 2),or (0, 3), or (0, 4) can work for all cases (FIG. 6A shows two CORESET#0 offsets as (0, 4)).

TABLE 3-1 CORESET#0 offsets needed for 51 RBs. Channel offset 0 1 2 3 45 Workable 0 0, 1 0, 1, 2 0, 1, 2, 3 1, 2, 3, 4 2, 3, 4, 5 CORESET#0offset

In another example, for the channelization of 20 MHz LBT bandwidth as 50RBs with respect to 30 kHz, for each given channel supported in NR-U,the possible offsets are illustrated in FIGS. 6B and 6C, and thecorresponding table is given in TABLE 3-2. Note that there are twocases, wherein either the highest RB (FIG. 6C) or lowest RB (FIG. 6B)from 51 RBs is truncated (e.g., due to guard band requirement). Then,two CORESET #0 offsets selected as (0, 3) can work for all cases (FIG.6B and FIG. 6C shows two CORESET #0 offsets as (0, 3)), or (0, 2) canwork for cases with lowest RB truncated.

FIG. 6B illustrates an example floating CORESET #0 in carriers with 50RBs 650 according to embodiments of the present disclosure. Anembodiment of the floating CORESET #0 in carriers with 50 RBs 650 shownin FIG. 6B is for illustration only. One or more of the componentsillustrated in FIG. 6B can be implemented in specialized circuitryconfigured to perform the noted functions or one or more of thecomponents can be implemented by one or more processors executinginstructions to perform the noted functions.

FIG. 6C illustrates another example floating CORESET #0 in carriers with50 RBs 670 according to embodiments of the present disclosure. Anembodiment of the floating CORESET #0 in carriers with 50 RBs 670 shownin FIG. 6C is for illustration only. One or more of the componentsillustrated in FIG. 6C can be implemented in specialized circuitryconfigured to perform the noted functions or one or more of thecomponents can be implemented by one or more processors executinginstructions to perform the noted functions.

TABLE 3-2 CORESET#0 offsets needed for 50 RBs. Channel offset 0 1 2 3 45 Workable CORESET#0 Invalid 0 0, 1 0, 1, 2 1, 2, 3 2, 3, 4 offset(lowest RB truncated) Workable CORESET#0 0 0, 1 0, 1, 2 1, 2, 3 2, 3, 43, 4, 5 offset (highest RB truncated)

For the channelization of 20 MHz LBT bandwidth as 49 RBs with respect to30 kHz, for each given channel supported in NR-U, the possible offsetsare illustrated in TABLE 3-3. Note that there are three cases, whereineither the highest 2 RBs or lowest 2 RBs or the highest and lowest RBfrom 51 RBs are truncated (e.g., due to guard band requirement). Then,three CORESET #0 offsets selected as (0, 2, 4) can work for all cases.

TABLE 3-3 CORESET#0 offsets needed for 49 RBs. Channel offset 0 1 2 3 45 Workable CORESET#0 invalid invalid 0 0, 1 1, 2 2, 3 offset (lowest 2RBs truncated) Workable CORESET#0 invalid 0 0, 1 1, 2 2, 3 3, 4 offset(highest and lowest RB truncated) Workable CORESET#0 0 0, 1 1, 2 2, 3 3,4 4, 5 offset (highest 2 RBs truncated)

For the channelization of 20 MHz LBT bandwidth as 48 RBs with respect to30 kHz, for each given channel supported in NR-U, the possible offsetsare illustrated in TABLE 3-4. Note that there are four cases, whereineither the highest 3 RBs or highest 2 with lowest 1, or highest 1 withlowest 2, or lowest 3 RBs from 51 RBs are truncated (e.g., due to guardband requirement). Then, 6 CORESET #0 offsets can work for all cases.

TABLE 3-4 CORESET#0 offsets needed for 48 RBs. Channel offset 0 1 2 3 45 Workable CORESET#0 invalid invalid invalid 0 1 2 offset (lowest 3 RBstruncated) Workable CORESET#0 invalid invalid 0 1 2 3 offset (highest 1and lowest 2 RBs truncated) Workable CORESET#0 invalid 0 1 2 3 4 offset(highest 2 and lowest 1 RBs truncated) Workable CORESET#0 0 1 2 3 4 5offset (highest 3 RBs truncated)

In one embodiment, the sub-RB-level offset is hard-coded in thespecification. In one example, for a given synchronization raster entry,and a given carrier bandwidth, the sub-RB-level offset is as given bythe examples in TABLE 1-1 to TABLE 1-6.

In one example, the sub-RB-level offset is indicated in PBCH payload.For one example, 5 bits are used for indicating the sub-RB-level offset,e.g., same as Rel-15 and denoted as k_SSB. In another example, candidatevalues for the sub-RB-level offset are given by {0, 2, 4, 6, 8, 10, 12,14, 16, 18, 20, 22}, and 4 bits (e.g., in MIB) are sufficient for thispurpose. In yet another example, candidate values for the sub-RB-leveloffset are given by {0, 4, 8, 12, 16, 20}, and 3 bits (e.g., in MIB) aresufficient for this purpose.

In one embodiment, the RB-level offset is hard-coded in thespecification. In one example, for a given synchronization raster entry,and a given carrier bandwidth, the RB-level offset is as given by theexamples in TABLE 1-1 to TABLE 1-6.

In another embodiment, the RB-level offset is indicated by PBCH payload(e.g., MIB), together with the multiplexing pattern with SSB, the numberof symbols for CORESET #0, and the bandwidth of CORESET #0, as part ofthe CORESET #0 configuration.

In one example, for {SCS_SSB, SCS_CORESET}={30 kHz, 30 kHz}, theRB-level offset is configurable from {0, 1, 2, 3, 4, 5} (note that thisset is the collection of all possible values needed as calculated inthis disclosure for SCS_SSB, SCS_CORESET}={30 kHz, 30 kHz}), and anexample configuration table is given by TABLE 4-1. In one example,reserved rows can be added to TABLE 4-1, such that the total number ofrows is 16 (e.g., maintaining the same table size as Rel-15).

TABLE 4-1 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {30 kHz, 30 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 48 1 0 1 1 48 1 1 21 48 1 2 3 1 48 1 3 4 1 48 1 4 5 1 48 1 5 6 1 48 2 0 7 1 48 2 1 8 1 48 22 9 1 48 2 3 10 1 48 2 4 11 1 48 2 5

In another example, for {SCS_SSB, SCS_CORESET}={30 kHz, 30 kHz}, theRB-level offset is configurable from a subset of {0, 1, 2, 3, 4, 5}. Inone instance, the CORESET #0 can be floating within the carrier bynoting that the BW of CORESET #0 is smaller than the BW of carrier, suchthat one configuration of RB-level offset can be reused for multiplecarriers. For instance, for {SCS_SSB, SCS_CORESET} {30 kHz, 30 kHz}, theBW of SSB is 48 RBs, and the BW of CORESET #0 is 51 RBs for 20 MHz, thenone configuration of the RB-level offset can be reused for carriers with4 different contiguous RB-level offset values and based on thecalculation in this disclosure, at most 6 different contiguous RB-leveloffset values from {0, 1, 2, 3, 4, 5} show up. Hence, at least 2configurations on the RB-level offset are sufficient.

An illustration of the floating CORESET #0 within the carrier is shownin FIG. 4-1 . In one consideration, although minimum number of requiredoffsets is 2, the number of supported offset to be configured can bemore than 2 to allow better flexibility, as long as the total number ofconfigurations can fit 4 bits as in NR Rel-15. Example configurationtables are given by TABLE 4-2 to TABLE 4-8. In one consideration to theexample tables, reserved rows can be added to TABLE 4-2 to TABLE 4-8,such that the total number of rows is 16 (e.g., maintaining the sametable size as Rel-15).

TABLE 4-2 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {30 kHz, 30 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 48 1 0 1 1 48 1 1 21 48 2 0 3 1 48 2 1

TABLE 4-3 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {30 kHz, 30 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 48 1 0 1 1 48 1 4 21 48 2 0 3 1 48 2 4

TABLE 4-4 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {30 kHz, 30 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 48 1 0 1 1 48 1 2 21 48 2 0 3 1 48 2 2

TABLE 4-5 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {30 kHz, 30 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 48 1 0 1 1 48 1 3 21 48 2 0 3 1 48 2 3

TABLE 4-6 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {30 kHz, 30 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 48 1 0 1 1 48 1 2 21 48 1 4 3 1 48 2 0 4 1 48 2 2 5 1 48 2 4

TABLE 4-7 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {30 kHz, 30 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 48 1 0 1 1 48 1 1 21 48 1 2 3 1 48 1 3 4 1 48 2 0 5 1 48 2 1 6 1 48 2 2 7 1 48 2 3

TABLE 4-8 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {30 kHz, 30 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 48 1 0 1 1 48 1 1 21 48 1 2 3 1 48 1 3 4 1 48 1 4 5 1 48 2 0 6 1 48 2 1 7 1 48 2 2 8 1 48 23 9 1 48 2 4

In yet another example, for {SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, theRB-level offset is configurable from {13, 14, 15, 16, 17, 18, 19, 20}(note that this set is the collection of all possible values needed ascalculated in this disclosure for SCS_SSB, SCS_CORESET}={15 kHz, 15kHz}), and an example configuration table is given by TABLE 5-1. Notethat this example assumes the SSB is located at the synchronizationraster as the reference to design the table when the SCS of SSB is 15kHz.

TABLE 5-1 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 48 1 13 1 1 48 1 142 1 48 1 15 3 1 48 1 16 4 1 48 1 17 5 1 48 1 18 6 1 48 1 19 7 1 48 1 208 1 48 2 13 9 1 48 2 14 10 1 48 2 15 11 1 48 2 16 12 1 48 2 17 13 1 48 218 14 1 48 2 19 15 1 48 2 20

In yet another example, for {SCS_SSB SCS_CORESET}={15 kHz, 15 kHz}, theRB-level offset is configurable from {0, 1, 2, 3, 4, 5, 6, 7} (note thatthis set is the collection of all possible values needed as calculatedin this disclosure for SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, with apredefined offset as 13 RB to define the values), and an exampleconfiguration table is given by TABLE 5-2. Note that this exampleassumes the SSB is located at 13 RBs from the synchronization raster asthe reference to design the table when the SCS of SSB is 15 kHz.

TABLE 5-2 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 48 1 0 1 1 48 1 1 21 48 1 2 3 1 48 1 3 4 1 48 1 4 5 1 48 1 5 6 1 48 1 6 7 1 48 1 7 8 1 48 20 9 1 48 2 1 10 1 48 2 2 11 1 48 2 3 12 1 48 2 4 13 1 48 2 5 14 1 48 2 615 1 48 2 7

In yet another example, for {SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, theCORESET #0 can be floating within the carrier by noting that the BW ofCORESET #0 is smaller than the BW of carrier, such that oneconfiguration of RB-level offset can be reused for multiple carriers.For instance, for {SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, the BW of SSBis 96 RBs, and the BW of CORESET #0 is 106 RBs for 20 MHz, then oneconfiguration of the RB-level offset can be reused for carriers with 11different contiguous RB-level offset values and based on the calculationin this disclosure, at most 11 different contiguous RB-level offsetvalues show up in TABLE 1-5 and TABLE 1-6. Hence, an exampleconfiguration table is given by TABLE 5-3, wherein X can be a valueselected from {10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21}, e.g.,X=10, or X=13, or X=20, or X=21, or X=17, or X=11. Note that thisexample assumes the SSB is located at the synchronization raster as thereference to design the table when the SCS of SSB is 15 kHz.

TABLE 5-3 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 96 1 X 1 1 96 2 X

In yet another example, for {SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, theCORESET #0 can be floating within the carrier by noting that the BW ofCORESET #0 is smaller than the BW of carrier, such that oneconfiguration of RB-level offset can be reused for multiple carriers.For instance, for {SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, the BW of SSBis 96 RBs, and the BW of CORESET #0 is 106 RBs for 20 MHz, then oneconfiguration of the RB-level offset can be reused for carriers with 11different contiguous RB-level offset values, and based on thecalculation in this disclosure, at most 11 different contiguous RB-leveloffset values show up in TABLE 1-5 and TABLE 1-6. Hence, an exampleconfiguration table is given by TABLE 5-3, wherein X can be a valueselected from {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11}, e.g., X=0, or X=3.Note that this example assumes the SSB is located at 10 RBs or 13 RBsfrom the synchronization raster as the reference to design the tablewhen the SCS of SSB is 15 kHz.

In yet another example, for {SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, theCORESET #0 can be floating within the carrier by noting that the BW ofCORESET #0 is smaller than the BW of carrier, such that oneconfiguration of RB-level offset can be reused for multiple carriers.For instance, for {SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, the BW of SSBis 96 RBs, and the BW of CORESET #0 is 106 RBs for 20 MHz, then oneconfiguration of the RB-level offset can be reused for carriers with 11different contiguous RB-level offset values.

Hence, an example configuration table is given by TABLE 5-4, wherein Xand Y can be a value selected from {10, 11, 12, 13, 14, 15, 16, 17, 18,19, 20, 21} such that Y−X≤10, e.g., {X, Y}={10, 20}, or {X, Y}={13, 20},or {X, Y}={13, 14}, or {X, Y}={19, 20}, or {X, Y}={20, 21}, or {X,Y}={10, 11}, or {X, Y}={10, 12}, or {X, Y}={10, 14}, or {X, Y}={10, 16},or {X, Y}={10, 18}, or {X, Y}={13, 21}, or {X, Y}={11, 21}. Note thatthis example assumes the SSB is located at the synchronization raster asthe reference to design the table when the SCS of SSB is 15 kHz.

TABLE 5-4 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 96 1 X 1 1 96 1 Y 21 96 2 X 3 1 96 2 Y

In yet another example, for {SCS_SSB, SCS_CORESET} {15 kHz, 15 kHz}, theCORESET #0 can be floating within the carrier by noting that the BW ofCORESET #0 is smaller than the BW of carrier, such that oneconfiguration of RB-level offset can be reused for multiple carriers.For instance, for {SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, the BW of SSBis 96 RBs, and the BW of CORESET #0 is 106 RBs for 20 MHz, then oneconfiguration of the RB-level offset can be reused for carriers with 11different contiguous RB-level offset values. Hence, an exampleconfiguration table is given by TABLE 5-4, wherein X and Y can be avalue selected from {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11} such thatY−X≤10, e.g., {X, Y}={0, 10}, or {X, Y}={3, 10}, or {X, Y}={0, 7}, or{X, Y}={0, 1}, or {X, Y}={3, 4}, or {X, Y}={9, 10}, or {X, Y}={10, 11},or {X, Y}={0, 2}, or {X, Y}={0, 4}, or {X, Y}={0, 6}, or {X, Y}={0, 8}.Note that this example assumes the SSB is located at 10 RBs or 13 RBsfrom the synchronization raster as the reference to design the tablewhen the SCS of SSB is 15 kHz.

In yet another example, for {SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, thenumber of offsets in the set of configurable offsets corresponding to{SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz} is the same as the number ofoffsets in the set of configurable offsets corresponding to {SCS_SSB,SCS_CORESET} {30 kHz, 30 kHz}, and the value of the offset in the set ofconfigurable offsets corresponding to {SCS_SSB, SCS_CORESET}={15 kHz, 15kHz} has a one-to-one mapping to the value of the offset in the set ofconfigurable offsets corresponding to {SCS_SSB, SCS_CORESET}={30 kHz, 30kHz}, e.g., O_15=O_30*2+10, wherein O_15 is the value of the offset inthe set of configurable offsets corresponding to {SCS_SSB,SCS_CORESET}={15 kHz, 15 kHz}, and O_30 is the value of the offset inthe set of configurable offsets corresponding to {SCS_SSB,SCS_CORESET}={30 kHz, 30 kHz}.

The example configuration tables for {SCS_SSB, SCS_CORESET}={15 kHz, 15kHz}, corresponding to TABLE 6-1 to TABLE 6-8, using the mappingrelationship of this example are shown in TABLE 6-1 to TABLE 6-8. In oneinstance, reserved rows can be added to TABLE 6-1 to TABLE 6-8, suchthat the total number of rows is 16 (e.g., maintaining the same tablesize as Rel-15).

TABLE 6-1 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 96 1 10 1 1 96 1 122 1 96 1 14 3 1 96 1 16 4 1 96 1 18 5 1 96 1 20 6 1 96 2 10 7 1 96 2 128 1 96 2 14 9 1 96 2 16 10 1 96 2 18 11 1 96 2 20

TABLE 6-2 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 96 1 10 1 1 96 1 122 1 96 2 10 3 1 96 2 12

TABLE 6-3 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 96 1 10 1 1 96 1 182 1 96 2 10 3 1 96 2 18

TABLE 6-4 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 96 1 10 1 1 96 1 142 1 96 2 10 3 1 96 2 14

TABLE 6-5 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 96 1 10 1 1 96 1 162 1 96 2 10 3 1 96 2 16

TABLE 6-6 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 96 1 10 1 1 96 1 142 1 96 1 18 3 1 96 2 10 4 1 96 2 14 5 1 96 2 18

TABLE 6-7 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 96 1 10 1 1 96 1 122 1 96 1 14 3 1 96 1 16 4 1 96 2 10 5 1 96 2 12 6 1 96 2 14 7 1 96 2 16

TABLE 6-8 Example CORESET #0 configuration table for {SCS_SSB,SCS_CORESET} = {15 kHz, 15 kHz} Multiplexing CORESET#0 No. of symbolsfor RB-level Index pattern BW CORESET #0 offset 0 1 96 1 10 1 1 96 1 122 1 96 1 14 3 1 96 1 16 4 1 96 1 18 5 1 96 2 10 6 1 96 2 12 7 1 96 2 148 1 96 2 16 9 1 96 2 18

In one example, for SS/PBCH block and CORESET multiplexing pattern 1,when multiple SCSs are supported for SS/PBCH block and its associatedCORESET #0, for a given configured bandwidth of CORESET #0, the numberof offsets in the set of configurable offsets corresponding to the givenCORESET #0 bandwidth is the same for all the supported SCSs, and thevalue of the offset in the set of configurable offsets corresponding tothe given CORESET #0 bandwidth has a one-to-one mapping relationshipamong all the supported SCSs.

For instance, for a given configured bandwidth of CORESET #0, and for afirst supported SCS_1 (i.e., {SCS_SSB, SCS_CORESET} {SCS_1, SCS_1}) anda second supported SCS_2 (i.e., {SCS_SSB, SCS_CORESET}={SCS_2, SCS_2}),a value of the offset in the set of configurable offsets correspondingto the first SCS (denoted as O_1) and a value of the offset in the setof configurable offsets corresponding to the second SCS (denoted as O_2)have the relationship as O_2=O_1*R_SCS+BW_SSB*R_SCS/2−BW_SSB/2, whereinR_SCS=SCS_1/SCS_2 is the ratio of SCSs, and BW_SSB is the BW of SS/PBCHblock in term of its SCS (e.g., BW_SSB=20 RBs). The generalization ofthis example is based on an assumption that SS/PBCH blocks withdifferent SCSs are center aligned on the same reference frequencylocation (e.g., a synchronization raster entry), and an illustration ofthe mapping relationship between different SCSs is shown in FIG. 7 .

FIG. 7 illustrates an example mapping relationship between SCSs 700according to embodiments of the present disclosure. An embodiment of themapping relationship between SCSs 700 shown in FIG. 7 is forillustration only. One or more of the components illustrated in FIG. 7can be implemented in specialized circuitry configured to perform thenoted functions or one or more of the components can be implemented byone or more processors executing instructions to perform the notedfunctions.

In yet another example, for {SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz}, thenumber of offsets in the set of configurable offsets corresponding to{SCS_SSB, SCS_CORESET}={15 kHz, 15 kHz} is the same as the number ofoffsets in the set of configurable offsets corresponding to {SCS_SSB,SCS_CORESET} {30 kHz, 30 kHz}, and the value of the offset in the set ofconfigurable offsets corresponding to {SCS_SSB, SCS_CORESET}={15 kHz, 15kHz} has a one-to-one mapping to the value of the offset in the set ofconfigurable offsets corresponding to {SCS_SSB, SCS_CORESET} {30 kHz, 30kHz}, e.g., O_15=O_30*2+Z, wherein O_15 is the value of the offset inthe set of configurable offsets corresponding to {SCS_SSB,SCS_CORESET}={15 kHz, 15 kHz}, O_30 is the value of the offset in theset of configurable offsets corresponding to {SCS_SSB, SCS_CORESET}={30kHz, 30 kHz}, and Z is a constant integer, e.g., Z=13

In one example, for SS/PBCH block and CORESET multiplexing pattern 1,when multiple SCSs are supported for SS/PBCH block and its associatedCORESET #0, for a given configured bandwidth of CORESET #0, the numberof offsets in the set of configurable offsets corresponding to the givenCORESET #0 bandwidth is the same for all the supported SCSs, and thevalue of the offset in the set of configurable offsets corresponding tothe given CORESET #0 bandwidth has a one-to-one mapping relationshipamong all the supported SCSs. For instance, for a given configuredbandwidth of CORESET #0, for a first supported SCS_1 (i.e., {SCS_SSB,SCS_CORESET} {SCS_1, SCS_1}) and a second supported SCS_2 (i.e.,{SCS_SSB, SCS_CORESET} {SCS_2, SCS_21}), a value of the offset in theset of configurable offsets corresponding to the first SCS (denoted asO_1) and a value of the offset in the set of configurable offsetscorresponding to the second SCS (denoted as O_2) have the relationshipas O_2=O_1*R_SCS+Z, wherein R_SCS=SCS_1/SCS_2 is the ratio of SCSs, andZ is a constant integer, e.g., Z=0.

FIG. 8 illustrates a flowchart of a method 800 for configuring CORESETaccording to embodiments of the present disclosure, as may be performedby a use equipment (UE) (e.g., 111-116 as illustrated in FIG. 1 ). Anembodiment of the method 800 shown in FIG. 8 is for illustration only.One or more of the components illustrated in FIG. 8 can be implementedin specialized circuitry configured to perform the noted functions orone or more of the components can be implemented by one or moreprocessors executing instructions to perform the noted functions.

As illustrated in FIG. 8 , the method 800 begins at step 802. In step802, the UE receives a synchronization signals and physical broadcastchannel (SS/PBCH) block.

Subsequently, the UE in step 804 determines a subcarrier spacing of theSS/PBCH block from a set of subcarrier spacings {SCS₁, SCS₂}.

Subsequently, the UE in step 806 determines a subcarrier spacing of atype0 physical downlink control channel (Type0-PDCCH) common searchspace (CSS) set in a control resource set (CORESET), wherein thesubcarrier spacing of the Type0-PDCCH CSS set is the same as thesubcarrier spacing of the SS/PBCH block.

Subsequently, the UE in step 808 determines a bandwidth of the CORESETbased on master information block (MIB) in the SS/PBCH block.

Subsequently, the UE in step 810 determines a number of symbols of theCORESET based on the MIB.

Next, the UE in step 812 determines, based on the MIB and the subcarrierspacing of the SS/PBCH block, a frequency offset from a set of frequencyoffsets {O₁, O₂}, wherein the frequency offset is determined as beingfrom a smallest resource block (RB) index of the CORESET to a smallestRB index of the common RB overlapping with a first RB of the SS/PBCHblock.

In step 812, O₁ and O₂ are determined, based on a one-to-one mapping, asgiven by O₂=O₁·R_(SCS)+BW_(SSB)−R_(SCS)/2−BW_(SSB)/2 whereR_(SCS)=SCS₁/SCS₂, and BW_(SSB) is a bandwidth of the SS/PBCH block in aunit of the RB.

In one embodiment, O₁ and O₂ are determined, based on a one-to-onemapping, as given by O₂=2·O₁+10.

Next, the UE in step 814 determines a frequency location of the CORESETbased on the determined frequency offset.

Finally, the UE in step 816 receives a Type0-PDCCH based on thedetermined bandwidth, the number of symbols, and the frequency locationof the CORESET.

In one embodiment, the UE determines the frequency offset as O₁ based ona determination of the subcarrier spacing of the SS/PBCH block as SCS₁and determines the frequency offset as O₂ based on a determination ofthe subcarrier spacing of the SS/PBCH block as SCS₂.

In one embodiment, the UE determines whether a shared spectrum channelaccess in a frequency range 1 (FR1) is supported and sets SCS₁ as a 30kHz, SCS₂ as a 15 kHz, and BW_(SSB) as 20 RBs based on a determinationthat the shared spectrum channel access in the FR1 is supported.

In one embodiment, the UE determines the subcarrier spacing of theSS/PBCH block as a 30 kHz and determines the frequency offset as one of0, 1, 2, or 3 RBs based on the MIB of the SS/PBCH block.

In one embodiment, the UE determines the subcarrier spacing of theSS/PBCH block as a 15 kHz and determines the frequency offset as one of10, 12, 14, or 16 RBs based on the MIB of the SS/PBCH block.

The above flowcharts illustrate example methods that can be implementedin accordance with the principles of the present disclosure and variouschanges could be made to the methods illustrated in the flowchartsherein. For example, while shown as a series of steps, various steps ineach figure could overlap, occur in parallel, occur in a differentorder, or occur multiple times. In another example, steps may be omittedor replaced by other steps.

Although the present disclosure has been described with an exemplaryembodiment, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims. None of the description in this application should be read asimplying that any particular element, step, or function is an essentialelement that must be included in the claims scope. The scope of patentedsubject matter is defined by the claims.

What is claimed is:
 1. A user equipment (UE) in a wireless communicationsystem, the UE comprising: a transceiver configured to receive asynchronization signals and physical broadcast channel (SS/PBCH) block;and a processor operably coupled to the transceiver, the processorconfigured to: determine a subcarrier spacing of the SS/PBCH block froma set of subcarrier spacings {15, 30} kilohertz (kHz); upon determiningthe subcarrier spacing of the SS/PBCH block as 30 kHz, determine afrequency offset as one of 0, 1, 2, or 3 resource blocks (RBs) based ona configuration in a master information block (MIB) of the SS/PBCHblock; upon determining the subcarrier spacing of the SS/PBCH block as15 kHz, determine the frequency offset as one of 10, 12, 14, or 16 RBsbased on the configuration in the MIB of the SS/PBCH block; anddetermine a frequency location of a control resource set (CORESET) basedon the frequency offset, wherein the transceiver is further configuredto receive a type0 physical downlink control channel (Type0-PDCCH) basedon the frequency location of the CORESET.
 2. The UE of claim 1, whereinthe processor is further configured to: determine a bandwidth of theCORESET based on the configuration in the MIB, and determine a number ofsymbols of the CORESET based on the configuration in the MIB.
 3. The UEof claim 1, wherein: the processor is further configured to determine asubcarrier spacing of a Type0-PDCCH common search space (CSS) set in theCORESET, and the subcarrier spacing of the Type0-PDCCH CSS set is thesame as the subcarrier spacing of the SS/PBCH block.
 4. The UE of claim1, wherein the frequency offset is determined as being from a smallestRB index of the CORESET to a smallest RB index of a common RBoverlapping with a first RB of the SS/PBCH block.
 5. A base station (BS)in a wireless communication system, the BS comprising: a transceiverconfigured to transmit a synchronization signals and physical broadcastchannel (SS/PBCH) block; and a processor operably coupled to thetransceiver, the processor configured to: determine a subcarrier spacingof the SS/PBCH block from a set of subcarrier spacings {15, 30}kilohertz (kHz); upon determining the subcarrier spacing of the SS/PBCHblock as 30 kHz, determine a frequency offset as one of 0, 1, 2, or 3resource blocks (RBs) based on a configuration in a master informationblock (MIB) of the SS/PBCH block; upon determining the subcarrierspacing of the SS/PBCH block as 15 kHz, determine the frequency offsetas one of 10, 12, 14, or 16 RBs based on the configuration in the MIB ofthe SS/PBCH block; and determine a frequency location of a controlresource set (CORESET) based on the frequency offset, wherein thetransceiver is further configured to transmit a type0 physical downlinkcontrol channel (Type0-PDCCH) based on the frequency location of theCORESET.
 6. The BS of claim 5, wherein the processor is furtherconfigured to: determine a bandwidth of the CORESET based on theconfiguration in the MIB, and determine a number of symbols of theCORESET based on the configuration in the MIB.
 7. The BS of claim 5,wherein: the processor is further configured to determine a subcarrierspacing of a Type0-PDCCH common search space (CSS) set in the CORESET,and the subcarrier spacing of the Type0-PDCCH CSS set is the same as thesubcarrier spacing of the SS/PBCH block.
 8. The BS of claim 5, whereinthe frequency offset is determined as being from a smallest RB index ofthe CORESET to a smallest RB index of a common RB overlapping with afirst RB of the SS/PBCH block.
 9. A method for operating a userequipment (UE) in a wireless communication system, the methodcomprising: receiving a synchronization signals and physical broadcastchannel (SS/PBCH) block; determining a subcarrier spacing of the SS/PBCHblock from a set of subcarrier spacings {15, 30} kilohertz (kHz); basedon determining the subcarrier spacing of the SS/PBCH block as 30 kHz,determining a frequency offset as one of 0, 1, 2, or 3 resource blocks(RBs) based on a configuration in a master information block (MIB) ofthe SS/PBCH block; based on determining the subcarrier spacing of theSS/PBCH block as 15 kHz, determining the frequency offset as one of 10,12, 14, or 16 RBs based on the configuration in the MIB of the SS/PBCHblock; determining a frequency location of a control resource set(CORESET) based on the frequency offset; and receiving a type0 physicaldownlink control channel (Type0-PDCCH) based on the frequency locationof the CORESET.
 10. The method of claim 9, further comprising:determining a bandwidth of the CORESET based on the configuration in theMIB, and determining a number of symbols of the CORESET based on theconfiguration in the MIB.
 11. The method of claim 9, further comprising:determining a subcarrier spacing of a Type0-PDCCH common search space(CSS) set in the CORESET, wherein the subcarrier spacing of theType0-PDCCH CSS set is the same as the subcarrier spacing of the SS/PBCHblock.
 12. The method of claim 9, wherein the frequency offset isdetermined as being from a smallest RB index of the CORESET to asmallest RB index of a common RB overlapping with a first RB of theSS/PBCH block.